home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000824-20010305
/
000243_news@columbia.edu _Sat Feb 3 16:15:04 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id QAA15716
for <kermit.misc@cpunix.cc.columbia.edu>; Sat, 3 Feb 2001 16:15:04 -0500 (EST)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id QAA20053
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 3 Feb 2001 16:15:04 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id QAA15127
for kermit.misc@watsun.cc.columbia.edu; Sat, 3 Feb 2001 16:12:25 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: Master and server mode for receives?
Date: 3 Feb 2001 21:12:25 GMT
Organization: Columbia University
Message-ID: <95hs7p$eoi$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <h0Ue6.2760$9g3.354891@news3.cableinet.net>,
Mike Scott <mike@NOSPAMcomputersurgery.com> wrote:
: I have a requirement to transmit and receive data from a remote machine
: which, according to their documentation, is running Kermit in server mode.
: Their docs say that my Kermit should run in master mode.
:
: I've been able to transmit files without a problem, but when I attempt to
: receive, nothing happens. I believe the problem is that my Kermit software
: (TurboPower's AsyncPro VCL components for Borland Delphi) is waiting for the
: remote to start a send. IOW, AsyncPro doesn't understand the concept of
: working as a master when doing a receive.
:
It's the difference between RECEIVE (passive) and GET (active).
: Is this a standard part of the Kermit protocol? The remote docs show that I
: should be sending an Init packet, getting an Ack, then sending a Receive
: packet and then the remote will start sending. IOW, it appears that I have
: to give the remote a "kick" to get it to start sending.
:
You'll probably need another client, one that goes a bit beyond where Kermit
was in 1981. A good source for Kermit clients and servers is here:
http://www.columbia.edu/kermit/
- Frank